Thanks for this contribution! @hsu @dirk-thomas -- do we want to also allow boos unit test framework, or do we want gtest?

This patch seems to not register the executable as a test. So from the build system view it is just an executable which will never get invoked when running make run_tests.

In order to use anything other then gtest it should provide the same functionality which e.g. includes generation of xunit compatible result files etc. Therefore I would recommend to stick to gtest since catkin provides all of this out-of-the-box.

Actually I first wrote the test using gtest.
However, this project does not uses catkin but raw CMake, and it's not clear to me how I should link with gtest (I found no package providing the libgtest .so on my ubuntu), so I backed up to boost.

Indeed CTest stuff or equivalent is missing to declare this binary as a test and get it launched by buildfarms.

Note that I'm primarily interested in showing issue #49 up (and getting it fixed), not in setting a test framework up.

Cheers

I didn't recall that urdfdom is now a plain CMake project. Then catkin obviously does not matter and you are completely on your own with testing (and making it work / being executed on the farm).

@isucan So, what would be the plan for integrating the tests?

It is strictly necessary to add a dependency on a test framework? Given that this is quite a simple test, I guess we could just use a main that output EXIT_SUCCESS on test success or EXIT_FAILURE on test failure, and that the corresponding binary to generate a CTest test.
Alternatively we can add a CMake option off by default for building tests, so that the test framework is a dependency only if the user wants to build the tests.